SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Performance-enhancing proxy</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Performance-enhancing proxy</span></span>

</h1>

</header>

<b>Performance-enhancing proxies</b> (<b>PEPs</b>) are network agents designed to improve the end-to-end performance of some <a href="Communication_protocols" class="mw-redirect" title="Communication protocols">communication protocols</a>. PEP standards are defined in RFC 3135 (PEPs intended to mitigate link-related degradations) and RFC 3449 (TCP performance implications of network path asymmetry).

</p>

<div class="mw-heading mw-heading2"><h2 id="Classification">Classification</h2></div>

<p>Available PEP implementations use different methods to enhance performance.

</p>

<ul><li><b>Proxy type:</b> A PEP can either 'split' a connection or 'snoop' into it. In the first case, the proxy pretends to be the opposite endpoint of the connection in each direction, literally splitting the connection into two. In the latter case, the proxy controls the transmissions of the TCP segments in both directions, by ack filtering and reconstruction in the existing connection (see <a href="Protocol_spoofing" title="Protocol spoofing">protocol spoofing</a>). This is based on the OSI level of implementation of the PEP.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup></li>

<li><b>Distribution:</b> PEPs can be either integrated or distributed. Integrated PEP will run on a single box, while distributed PEP will require to be installed on both sides of the link that cause the performance degradation. This is quite common in commercial PEP devices, which act as a <a href="Black_box" title="Black box">black box</a>, using more or less open protocols to communicate between them in the place of TCP.</li>

<li><b>Symmetry: </b>A PEP implementation may be symmetric or asymmetric. Symmetric PEPs use identical behavior in both directions; the actions taken by the PEP occur independent from which interface a packet is received. Asymmetric PEPs operate differently in each direction, which can cause, for example, only one link direction performance to be enhanced.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Types">Types</h2></div>

<p>There are a range of different types of PEPs. Each is used to solve a link related problem. Some common types include:

</p>

<ul><li>Split-TCP</li>

<li>Ack decimation</li>

<li>Snoop</li>

<li>D-proxy</li></ul>

<div class="mw-heading mw-heading3"><h3 id="Split_TCP">Split TCP</h3></div>

<p>Split TCP is typically used to solve TCP problems with large <a href="Round-trip_delay_time" class="mw-redirect" title="Round-trip delay time">round-trip delay times</a>. A typical system uses Split TCP PEPs to improve <a href="Transmission_Control_Protocol" title="Transmission Control Protocol">TCP</a> performance over a <a href="Satellite_link" class="mw-redirect" title="Satellite link">satellite link</a>. Split TCP functions by breaking the <a href="End-to-end_connection" class="mw-redirect" title="End-to-end connection">end-to-end connection</a> into multiple connections and using different parameters to transfer data across the different legs. The end systems use standard TCP with no modifications, and do not need to know of the existence of the PEPs in between. Split TCP intercepts TCP connections from the end systems and terminates them. This allows the end systems to run unmodified and can overcome some problems with TCP window sizes on the end systems being set too low for satellite communications.

</p>

<div class="mw-heading mw-heading3"><h3 id="Ack_filtering/decimation">Ack filtering/decimation</h3></div>

<p>Ack filtering or decimation is used on highly <a href="Asymmetry" title="Asymmetry">asymmetric</a> links. In asymmetric links the upstream and downstream rates vary widely. A common example is satellite broadband where a downstream satellite link provides significantly greater bandwidths than the upstream dialup modem link. In this scenario, the speed at which the modem can return TCP acknowledgements can be a limiting factor. As TCP acknowledgements are cumulatively acknowledged some can be decimated or filtered to improve performance.

</p>

<div class="mw-heading mw-heading3"><h3 id="Snoop">Snoop</h3></div>

<p>The Snoop proxy<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> is an example of an integrated proxy. It is designed to hide interference or collision-based <a href="Packet_loss" title="Packet loss">packet loss</a> over a wireless link. Snoop proxies detect losses by monitoring TCP transmissions for duplicate acknowledgements. When duplicate TCP acknowledgements, indicating a packet loss, are received by Snoop, they will be silently dropped and lost data packet will be retransmitted. The TCP sender should have no knowledge of the loss. This should prevent TCP senders from unnecessarily reducing the TCP window.

</p>

<div class="mw-heading mw-heading3"><h3 id="D-Proxy">D-Proxy</h3></div>

<p>D-Proxy<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> is also designed to hide interference or collision based packet loss over a wireless link. D-Proxy is a new distributed TCP proxy, requiring a proxy on either side of the lossy link. Like Snoop, it uses TCP sequence numbers to detect lost packets. However, it has a proactive approach, monitoring the TCP sequence numbers on data packets rather than acknowledgements. When packet loss occurs, the TCP stream will be temporarily buffered until the missing packet can be recovered and re-sequenced.

</p>

<ul><li><a href="Proxy_server" title="Proxy server">Proxy server</a></li>

<li><a href="TCP_congestion_control" title="TCP congestion control">TCP congestion control</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external autonumber" href="http://techblog.aasisvinayak.com/performance-enhancement-proxy-pep-tcp-in-wireless-network-part-3/">[1]</a>: PERFORMANCE ENHANCEMENT PROXY (PEP) : TCP in Wireless Network</span>

</li>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFBalakrishnanSrinivasan_SeshanRandy_H._Katz1995" class="citation journal cs1">Balakrishnan, Hari; Srinivasan Seshan; Randy H. Katz (December 1995). "Improving TCP/IP Performance over Wireless Networks". <i>ACM Wireless Networks</i>. <b>1</b> (4). <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2FBF01985757">10.1007/BF01985757</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:2204005">2204005</a>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite id="CITEREFMurrayTerry_KoziniecMichael_Dixon2009" class="citation journal cs1">Murray, David; Terry Koziniec; Michael Dixon (2009). "Solving Ack Inefficiencies in 802.11 Networks". <i>IEEE International Conference on Internet Multimedia Systems Architecture and Applications</i>.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite id="CITEREFMurrayTerry_KoziniecMichael_Dixon2010" class="citation journal cs1">Murray, David; Terry Koziniec; Michael Dixon (2010). "D-Proxy: Reliability in Wireless Networks". <i>16th Asia-Pacific Conference on Communications (APCC)</i>.</cite></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="http://sf.net/projects/pepsal">PEPsal</a> : A <a href="GPL" class="mw-redirect" title="GPL">GPL</a> licensed, <a href="Linux" title="Linux">Linux</a>-based, integrated splitting PEP implementation</li>

<li><a rel="nofollow" class="external text" href="http://mediasputnik.ru/en/product/2402.shtml">PEP server MediaSputnik</a> : PEP server MediaSputnik 2402 has been developed by MediaSputnik as I-PEP compatible server compliant with SatLabs Group (ESA) recommendations to support DVB-RCS standards and networks</li>

<li><a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc3135">RFC 3135</a> : The whole RFC (Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations)</li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-01-03" href="https://en.wikipedia.org/wiki/?title=Performance-enhancing_proxy&oldid=1266991013">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>